Mission Accomplished
[ Close & Return to Lab ]
📄 Mission Debrief: Voice VLANs & Trunking
×
1. The "Why": Broadcast Domains
Implementing VLANs allows you to segment a single switch into multiple logical networks. This improves security (HR can't see Sales traffic) and performance (broadcast containment).
2. New Concept: Voice VLAN (Auxiliary VLAN)
In modern offices, computers often plug into the back of a VoIP phone, which then plugs into the wall.
This creates a unique problem: We need two VLANs on a single access port.
When you type switchport voice vlan 110, the switch tells the phone via CDP/LLDP to tag its own traffic with ID 110, while passing PC traffic through untagged.
3. Deep Dive: IEEE 802.1Q Tagging
Trunks use Tagging to identify which VLAN a frame belongs to.
[ Dest MAC ] [ Src MAC ] [ 802.1Q TAG ] [ EtherType ] [ DATA ] [ FCS ]
The Untagged Rule: Traffic belonging to the Native VLAN (and Data VLAN on an endpoint) is sent across the trunk without a tag.
4. Topology Reference (Answer Key)
Use this to verify your final configuration:
5. Command Cheat Sheet
Trunk Config (Uplinks):
sw mode trunk ! Force Trunk Mode sw trunk encap dot1q ! Define Protocol sw trunk allowed vlan add 10,110 ! Allow Data + Voice
Endpoint Config (PCs & Phones):
sw mode access ! Force Access Mode sw access vlan 10 ! Assign Data VLAN sw voice vlan 110 ! Assign Voice VLAN no sw access vlan ! RESET PORT (Wipes Data & Voice)
VLAN Database
🗄️
DB-SRV1
VLAN 50
CORE SWITCH10.10.x.1
🌐
WEB-SRV1
VLAN 50
Gi1/0/1 ↔ Gi0/1
ACCESS SWITCHUplink